Can't use ULA addresses in NAT64 #1878
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the PR! ❤️ |
hjensas
force-pushed
the
nat64-switch-addresses
branch
from
5b0decc to
29581c0
Compare
hjensas
force-pushed
the
nat64-switch-addresses
branch
from
29581c0 to
99c3240
Compare
hjensas
force-pushed
the
nat64-switch-addresses
branch
from
99c3240 to
39d7b21
Compare
hjensas
force-pushed
the
nat64-switch-addresses
branch
from
39d7b21 to
f9d53ee
Compare
Ran into an issue where routing on the OCP cluster gets confused by the use of ULA addresses on the machine network. OCP uses ULA addresses for internal networks, OVN kubernetes for example. When using ULA addressing on the machine network there is race when building the routing tables - and in some cases the hosts end up using the wrong source address in outgoing traffic. To fix this, switch to GUA addresses.
hjensas
force-pushed
the
nat64-switch-addresses
branch
from
f9d53ee to
3e57f50
Compare
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cjeanner The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
rebtoor
approved these changes
Jun 18, 2024
openshift-merge-bot
bot
merged commit 1950573
into
openstack-k8s-operators:main
6 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ran into an issue where routing on the OCP cluster gets confused by the use of ULA addresses on the machine network.
OCP uses ULA addresses for internal networks, OVN kubernetes for example. When using ULA addressing on the machine network there is race when building the routing tables - and in some cases the hosts end up using the wrong source address in outgoing traffic.
To fix this, switch to GUA addresses.
As a pull request owner and reviewers, I checked that: